|
|
|
Send these Clients Packing
Consider using Virtual Loadable Modules (VLMs) as your client drivers if you're running on a NetWare network. (Yes, they're stable.) Retire the monolithic clients SHELLGEN and WSGEN generated in older NetWare versions.
Having TCP/IP problems? Sure you've got a valid connection? Try this: Go to the DOS prompt. Type ping 198.105.232.1
(the IP address of Microsoft's ftp server) or ping 128.95.1.4
(the Microsoft DNS server). If it works, you know TCP/IP is working and you have a good connection. Now, check your local Domain Name Service (DNS). Type ping FTP.MICROSOFT.COM
. If this works, then your DNS settings are correct and operating. Look elsewhere for the problem. If you're behind a firewall, this won't work. Check with your network administrator and ping the firewall server address instead.
Problems with NWPOPUP, the Windows-based NetWare message display utility, are common. There's a known problem with NWPOPUP.EXE versions dated earlier than 03/10/92 and Windows running in 386 Enhanced mode. Get a newer version of the utility.
Create a log file of your attempts to get dial-up TCP/IP working in Win95. Choose Control Panel/Networks/"Dial-Up adapter"/Properties/Advanced. Set "Record a log file" to Yes. Win95 will create a log file--called PPPLOG.TXT--in your Windows directory. After a session, view the text file to see what's going on.
Solve Winsock--Windows' TCP/IP stack's so-called common socket--anomalies in several ways. The application may require a specific WINSOCK.DLL file, which may not work with Win95. Some Winsock applications copy their own WINSOCK.DLL files into the application's directory, and this can be a trouble source. To see if your application can use the new Winsock version, rename the application's WINSOCK.DLL so that it's using only the Win95 WINSOCK.DLL in the Windows directory. If the application doesn't work with Microsoft's Win95 WINSOCK.DLL file, you may have to copy the application's WINSOCK.DLL file over Win95's--not the best course of action. You're better off getting an updated version of the application that works with Win95's WINSOCK.DLL. Finally, ensure that another WINSOCK.DLL version doesn't show up in the path ahead of the one you're trying to run. Type dir WINSOCK.DLL /S
at a command prompt in the root directory or use the Win95 Find tool to see how many copies of the file are littering your hard disk.
If you're using TCP/IP on a WAN (wide area network) bound to both the LAN and PPP adapter without a DHCP server on the LAN, you may notice a two- to three-second pause when the computer accesses the network. To eliminate the delay, unbind the TCP/IP protocol from your LAN adapter. To do this, Select Network Control Panel/Properties, then uncheck TCP/IP in the bindings property tab.
It's easy to access a Windows for Workgroups shared disk drive from DOS without starting WFWG--if you want to use your machine as a client and not a server. Type the net logon
command at the DOS prompt. Be prepared to use a huge chunk of conventional memory for this privilege.
To use NetBIOS applications for a DOS application, start NetBIOS by entering net start netbind
. Then, if you want to use the NETBEUI protocol, enter net start netbeui
. You'll then have access to NetBIOS even for DOS applications--without using WFWG.
If you're running NT and you missed the diagnostic information MSD provided in the Windows environment, don't worry. Try running \WINNT\SYSTEM32\WINMSD.EXE
. This utility displays a multitude of information, including OS version, hardware, memory, drivers, services, devices, IRQ/port status, DMA/memory, environment, network and drives.
Most of NT's help files are located in the \WINNT\SYSTEM32 directory and have the extension .HLP. Although you can get to them eventually via the main help system, double-clicking on them to pull up help on any topic is the quicker way to go.
|
|
|